Belief & evidence in empirical software engineering
نویسندگان
چکیده
Empirical software engineering has produced a steady stream of evidence-based results concerning the factors that affect important outcomes such as cost, quality, and interval. However, programmers often also have strongly-held a priori opinions about these issues. These opinions are important, since developers are highlytrained professionals whose beliefs would doubtless affect their practice. As in evidence-based medicine, disseminating empirical findings to developers is a key step in ensuring that the findings impact practice. In this paper, we describe a case study, on the prior beliefs of developers at Microsoft, and the relationship of these beliefs to actual empirical data on the projects in which these developers work. Our findings are that a) programmers do indeed have very strong beliefs on certain topics b) their beliefs are primarily formed based on personal experience, rather than on findings in empirical research and c) beliefs can vary with each project, but do not necessarily correspond with actual evidence in that project. Our findings suggest that more effort should be taken to disseminate empirical findings to developers and that more in-depth study the interplay of belief and evidence in software practice is needed.
منابع مشابه
The Dangerous Dogmas of Software Engineering
To legitimize itself as a scientific discipline, the software engineering academic community must let go of its non-empirical dogmas. A dogma is belief held regardless of evidence. This paper analyzes the nature and detrimental effects of four software engineering dogmas – 1) the belief that software has “requirements”; 2) the division of software engineering tasks into analysis, design, coding...
متن کاملOn the Representation and Aggregation of Evidence in Software Engineering: A Theory and Belief-based Perspective
An adequate representation and a feasible aggregation procedure of evidence represents a challenging problem in many disciplines. The right representation can help scientists discuss and present the results of their findings and, if it is simple enough, it can be useful for practitioners to base their decisions on improvement implementations. The aggregation strengthens confidence in comparison...
متن کاملHas Twenty-five Years of Empirical Software Engineering Made a Difference?
Our activities in software engineering typically fall into one of three categories, (1) to invent new phenomena, (2) to understand existing phenomena, and (3) to facilitate inspirational education. This paper explores the place of empirical software engineering in the first two of these activities. In this exploration evidence is drawn from the empirical literature in the areas of software insp...
متن کاملEvidence of Usage-Based Reading Effects by Using the Structured Synthesis Method (SSM)
In this technical report, we present an example of the Structured Synthesis Method (SSM). For this example, we chose the classical domain of Software Inspection, in this case, the UBR inspection technique. This domain was deliberately chosen because it is a well-known domain in SE, particularly within the Empirical Software Engineering community where it has been extensively investigated and wa...
متن کاملInvestigating Adoption of Agile Software Development Methodologies in Organisations
This paper reports on the research published between the years 1997 and 2003inclusive in the journal of Empirical Software Engineering, drawing on thetaxonomy developed by Glass et al. in [2]. We found that the research wassomewhat narrow in topic with about half the papers focusing onmeasurement/metrics, review and inspection; that researchers were almost asinterested i...
متن کاملذخیره در منابع من
با ذخیره ی این منبع در منابع من، دسترسی به آن را برای استفاده های بعدی آسان تر کنید
عنوان ژورنال:
دوره شماره
صفحات -
تاریخ انتشار 2016